1. Should @click:prepend work at this stage? Because it doesn't form me

<template>
  <v-app>
    <v-main>
      <v-select :items="['a', 'b', 'c']" prepend-icon="mdi-vuetify" clearable @click:prepend="c" />
    </v-main>
  </v-app>
</template>

<script setup>
  const c = e => console.log(e)
</script>

2. Not a fan of current transition for items menu, not only visually but also quick clicking on the option after opening the menu hides the menu without seleting the option. There's no menuProps any more to turn off transtiion, is there another way?

3. Clearable icon shows only on hover, not sure if that's a good idea. Found the persistent-clear prop, I think it should be default true

4. Keyboard navigation doesn't work (arrows and typing letters, only enter/space works for opening the menu)

1. Should @click:prepend work at this stage? Because it doesn't form me

2. Not a fan of current transition for items menu, not only visually but also quick clicking on the option after opening the menu hides the menu without seleting the option. There's no menuProps any more to turn off transtiion, is there another way?

3. Clearable icon shows only on hover, not sure if that's a good idea. Found the persistent-clear prop, I think it should be default true

4. Keyboard navigation doesn't work (arrows and typing letters, only enter/space works for opening the menu)

1. Yes, I'll look into it
2. This requires changes to how v-menu works, will be separate from this PR
3. This matches the default text input functionality and I don't like boolean true default properties
4. This is the responsibility of v-menu and v-list. It will come as a separate composable that's integrated into nested.

3. This matches the default text input functionality and I don't like boolean true default properties

Could be done with different property name, ex. show-clear-only-on-hover (not that exact name but you get the idea). I agree that that's not the scope of this PR though